]> dgit.raspbian.org Git - gnome-shell.git/log
gnome-shell.git
6 years agounlockDialog: Remove 'Login as another user' Label
Umang Jain [Sat, 1 Feb 2020 15:23:59 +0000 (20:53 +0530)]
unlockDialog: Remove 'Login as another user' Label

According to the new mockups, logging in as another user
should be handled by the (<) button present on the lock-screen.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/922

6 years agoauthPrompt: Iconize the cancel button
Umang Jain [Tue, 14 Jan 2020 15:15:48 +0000 (20:45 +0530)]
authPrompt: Iconize the cancel button

Replace the "Cancel" label in the cancel button
by an arrow icon, and adjust the theme to make
it circular.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/922

6 years agoauthPrompt: Move cancel button, entry and spinner to a single row
Umang Jain [Tue, 14 Jan 2020 19:02:24 +0000 (00:32 +0530)]
authPrompt: Move cancel button, entry and spinner to a single row

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/922

6 years agoauthPrompt: Remove Next button and its references
Umang Jain [Tue, 14 Jan 2020 15:04:26 +0000 (20:34 +0530)]
authPrompt: Remove Next button and its references

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/922

6 years agouserWidget: Allow vertical orientation for user avatars
Umang Jain [Tue, 14 Jan 2020 14:53:36 +0000 (20:23 +0530)]
userWidget: Allow vertical orientation for user avatars

Allow vertical orientation for the userWidget so that the user-avatar
can be centered and user's name can be placed below it. The plan
for 3.36 is to use this vertical userWidget layout for both lock
and login screen.

The userWidget is also used while creating the user-selection list
at the login, hence we still need to keep the horizontal layout
for userWidget in place.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/922

6 years agotheme: Make base icon size font-relative
Florian Müllner [Wed, 12 Feb 2020 18:46:44 +0000 (19:46 +0100)]
theme: Make base icon size font-relative

Most icons are used along-side text, like the top bar or menus.
It therefore makes sense for them to adjust along-side the text
when the text-scaling changes.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/995

6 years agoUpdate Turkish translation
Emin Tufan Çetin [Wed, 12 Feb 2020 17:42:05 +0000 (17:42 +0000)]
Update Turkish translation

6 years agoicons: update Extensions app icon
Jakub Steiner [Tue, 11 Feb 2020 12:09:02 +0000 (13:09 +0100)]
icons: update Extensions app icon

- use more geometric shapes, no tilt
- everything tends to be blue, use green instead

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/994

6 years agounlockDialog: Multiply blur sigma value with the scale factor
Jonas Dreßler [Tue, 11 Feb 2020 19:19:50 +0000 (20:19 +0100)]
unlockDialog: Multiply blur sigma value with the scale factor

Since the blur sigma decides how many pixels get factored in when
blurring and setting a scale factor increases the background texture by
that factor, the sigma value should also be multiplied by the scale
factor.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agoblur-effect: Remove modify_paint_volume vfunc override
Jonas Dreßler [Mon, 10 Feb 2020 14:27:34 +0000 (15:27 +0100)]
blur-effect: Remove modify_paint_volume vfunc override

If we modify the paint volume to make it larger and include the blur
radius, we should also use the gained size and draw something there.
Since the framebuffers are only the size of the actor to blur, we're not
doing that right now anyway, so remove the vfunc override.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agoblur-effect: Use sigma value instead of blur radius
Jonas Dreßler [Mon, 10 Feb 2020 14:34:57 +0000 (15:34 +0100)]
blur-effect: Use sigma value instead of blur radius

Almost all implementations, including CSS [1] of gaussian blurs use the
sigma/standard deviation value as the input parameter, even if they call
that value "radius". Since using sigma is more correct mathematically
and avoids confusion for people used to other blur implementations, use
that parameter here, too.

[1] https://www.w3.org/TR/filter-effects-1/#funcdef-filter-blur

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agoblur-effect: Implement incremental calculation of gauss coefficient
Jonas Dreßler [Mon, 10 Feb 2020 14:34:03 +0000 (15:34 +0100)]
blur-effect: Implement incremental calculation of gauss coefficient

Use the shader for linear sampling and incremental calculation of the
gaussian kernel values as it was implemented by Patrick Walton in
webrender.

The sigma value for the blur (the standard deviation) is calculated by
taking the blur radius and dividing it by 3, this value is used by most
implementations of gaussian blurs since it covers a high percentage of
the gaussian shape.

The linear sampling optimization is implemented by skipping every second
texel (i += 2) in the for-loop that's sampling adjacent texels.

https://github.com/servo/webrender/blob/master/webrender/res/cs_blur.glsl
https://github.com/servo/webrender/commit/38ec7db6f165ff7aaad12d91eca7d7a5f51557b5

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agoblur-effect: Only apply paint opacity once when blurring actor
Jonas Dreßler [Fri, 7 Feb 2020 09:23:20 +0000 (10:23 +0100)]
blur-effect: Only apply paint opacity once when blurring actor

We don't want to apply the opacity multiple times, because this would
also multiply the opacity we're applying.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agoblur-effect: Only apply paint opacity to actor blur
Jonas Dreßler [Fri, 7 Feb 2020 09:21:21 +0000 (10:21 +0100)]
blur-effect: Only apply paint opacity to actor blur

We don't want to apply the opacity of the actor when blurring the
background.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agoblur-effect: Don't paint background using actor opacity
Jonas Dreßler [Fri, 7 Feb 2020 09:10:58 +0000 (10:10 +0100)]
blur-effect: Don't paint background using actor opacity

The background should always be painted fully opaque, the opacity of the
actor does not change the one of the background.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agoblur-effect: Use int for opacity override
Jonas Dreßler [Fri, 7 Feb 2020 09:08:13 +0000 (10:08 +0100)]
blur-effect: Use int for opacity override

The opacity override can be -1 if no override is set, so use the
appropriate datatype here.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agoblur-effect: Floor downscaled frambuffer sizes
Jonas Dreßler [Mon, 10 Feb 2020 14:22:33 +0000 (15:22 +0100)]
blur-effect: Floor downscaled frambuffer sizes

Floor the downscaled size of the new framebuffer to make sure we don't
initialize a framebuffer with a floating point value that might be
interpreted wrong by `cogl_texture_2d_new_with_size` and end up with a
slightly wrong aspect ratio of the framebuffer.

This fixes situations where the widths or heights of downscaled
framebuffers sometimes miss some pixels at the border.

While at it, remove the `downscale_factor` argument from
`setup_projection_matrix` since that function doesn't need the initial
size of the actor anyway.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agoblur-effect: Add some more documentation about performance
Jonas Dreßler [Mon, 10 Feb 2020 14:21:29 +0000 (15:21 +0100)]
blur-effect: Add some more documentation about performance

Explicitly mention that this effect works best for large blur radii and
can be slow if the blurred actor/image is large and not being scaled.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agoblur-effect: Fix crash when switching to ACTOR mode
Jonas Dreßler [Mon, 10 Feb 2020 14:20:51 +0000 (15:20 +0100)]
blur-effect: Fix crash when switching to ACTOR mode

The `clear_framebuffer()` function takes a CoglFramebuffer, not a
FramebufferData object.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/991

6 years agotheme: revert window picker whitespace
Jakub Steiner [Mon, 10 Feb 2020 19:19:22 +0000 (20:19 +0100)]
theme: revert window picker whitespace

- revert to the more compact overview, providing more space for the
  window thumbnails.

Fixes https://gitlab.gnome.org/GNOME/gnome-shell/issues/2187

6 years agoUpdate Japanese translation
sicklylife [Tue, 11 Feb 2020 17:48:15 +0000 (17:48 +0000)]
Update Japanese translation

6 years agoUpdate Japanese translation
sicklylife [Tue, 11 Feb 2020 17:43:06 +0000 (17:43 +0000)]
Update Japanese translation

6 years agoUpdate Catalan translation
Jordi Mas [Tue, 11 Feb 2020 12:08:55 +0000 (13:08 +0100)]
Update Catalan translation

6 years agoUpdated Spanish translation
Daniel Mustieles [Tue, 11 Feb 2020 11:18:16 +0000 (12:18 +0100)]
Updated Spanish translation

6 years agoextensions-tool: Add option to list updates
Florian Müllner [Sat, 30 Nov 2019 18:52:42 +0000 (19:52 +0100)]
extensions-tool: Add option to list updates

Now that we support extension updates, it may be useful to list
pending updates from the command line. It's easy enough to support,
so add a corresponding option to the list command.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/988

6 years agobackground: Remove noise texture
Georges Basile Stavracas Neto [Wed, 5 Feb 2020 14:21:30 +0000 (11:21 -0300)]
background: Remove noise texture

Use the plain background color.

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2174
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Remove lock screen group from Crtl-Alt-Tab manager
Georges Basile Stavracas Neto [Thu, 30 Jan 2020 15:17:07 +0000 (12:17 -0300)]
screenShield: Remove lock screen group from Crtl-Alt-Tab manager

There is nothing else to be focused in the lock screen itself -- the
top bar is already handled elsewhere, and the dialog manages itself
now.

Remove the lock screen group from the Ctrl-Alt-Tab manager.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Cleanup _ensureUnlockDialog
Georges Basile Stavracas Neto [Mon, 2 Dec 2019 15:36:38 +0000 (12:36 -0300)]
screenShield: Cleanup _ensureUnlockDialog

Just like on ScreenShield.activate(), we can just ensure the
unlock screen on ScreenShield.showDialog().

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Rework key focus management
Georges Basile Stavracas Neto [Mon, 2 Dec 2019 15:35:00 +0000 (12:35 -0300)]
screenShield: Rework key focus management

Instead of always grabbing key focus for the screen lock
group, do that for the unlock dialog itself.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Create auth prompt on demand
Georges Basile Stavracas Neto [Mon, 2 Dec 2019 14:01:20 +0000 (11:01 -0300)]
unlockDialog: Create auth prompt on demand

AuthPrompt is the set of actors that contain the user avatar,
the username, and the password entry. With the removal of the
screen shield, the unlock dialog (be it UnlockDialog or the
LoginDialog) is always created, and in the case of UnlockDialog,
so is the auth prompt.

This is problematic, though, since for passwordless accounts,
the simple act of creating AuthPrompt authenticates the user,
and lifts the lock screen.

Create the AuthPrompt on demand in UnlockDialog.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Add .critical CSS class to critical notifications
Georges Basile Stavracas Neto [Wed, 5 Feb 2020 14:58:57 +0000 (11:58 -0300)]
unlockDialog: Add .critical CSS class to critical notifications

As per the latest lock screen mockups, critical notifications must have
a more prominent, solid color.

Add a .critical style class to critical notification bubbles, and make
them darker.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agotheme: Adjust style of lock screen notifications
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 19:08:20 +0000 (16:08 -0300)]
theme: Adjust style of lock screen notifications

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Line notification labels horizontally
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 19:05:45 +0000 (16:05 -0300)]
unlockDialog: Line notification labels horizontally

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Use just the counter to format notifications
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 19:05:12 +0000 (16:05 -0300)]
unlockDialog: Use just the counter to format notifications

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Show clock when canceling or failing auth
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 19:14:26 +0000 (16:14 -0300)]
unlockDialog: Show clock when canceling or failing auth

There is still a problem of focus not going to the entry after the
first cancel, but it seems to work fine otherwise.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Toggle between clock and auth prompt
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 17:37:10 +0000 (14:37 -0300)]
unlockDialog: Toggle between clock and auth prompt

Toggle between them when (1) tapping anythere on the screen, and
(2) pressing any key.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Move auth prompt and clock to a ShellStack
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 17:36:01 +0000 (14:36 -0300)]
unlockDialog: Move auth prompt and clock to a ShellStack

We will toggle between each other in the next commit, so add
both to a ShellStack.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Remove key press event handler
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 17:33:26 +0000 (14:33 -0300)]
screenShield: Remove key press event handler

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Introduce UnlockDialogLayout
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 16:36:47 +0000 (13:36 -0300)]
unlockDialog: Introduce UnlockDialogLayout

This is the layout manager responsible for ensuring
that the clock is always at the third of the screen
height, and the notifications can push it to above.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agotheme: Adjust lock screen clock fonts
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 15:52:47 +0000 (12:52 -0300)]
theme: Adjust lock screen clock fonts

These values were decided during the GNOME Shell Hackfest, but
they're still subject to changes.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agosessionMode: Remove lock-screen mode
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 15:43:18 +0000 (12:43 -0300)]
sessionMode: Remove lock-screen mode

Now that the screen shield is gone (at least, as it used to
be), the corresponding session mode is not necessary anymore
as well.

Remove the 'lock-screen' session mode, and the corresponding
CSS.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Move lock shield below dialog
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 15:30:23 +0000 (12:30 -0300)]
screenShield: Move lock shield below dialog

Pretty much what the commit title says.

This gives the lock shield actor another role: instead of
being the interactive screen shield, make it the invisible
actor that prevents interacting with windows while the
unlock dialog is sliding down.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Only animate the unlock dialog
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 15:29:41 +0000 (12:29 -0300)]
screenShield: Only animate the unlock dialog

Remove the slide-up-down animation from the lock shield.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Rename _liftShield to _activateDialog
Georges Basile Stavracas Neto [Thu, 30 Jan 2020 14:30:55 +0000 (11:30 -0300)]
screenShield: Rename _liftShield to _activateDialog

Lifting the shield is now what happens *after* successfully logging
in, not before. Now, what we do is activate the dialog before logging
in.

Rename the method to reflect that.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Activate dialog when necessary
Georges Basile Stavracas Neto [Thu, 30 Jan 2020 14:44:43 +0000 (11:44 -0300)]
screenShield: Activate dialog when necessary

Activating a dialog is slightly different from opening it; the
former is about showing the user authentication widgetry, while
the latter is about creating it and pre-allocating the necessary
resources.

Activate the screen shield dialog when necessary.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Lift the unlock dialog
Georges Basile Stavracas Neto [Fri, 29 Nov 2019 15:24:17 +0000 (12:24 -0300)]
screenShield: Lift the unlock dialog

Instead of scaling it, lift the unlock dialog when unlocking,
and vice-versa.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Remove scrolling
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 23:11:17 +0000 (20:11 -0300)]
screenShield: Remove scrolling

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Cleanup unused method arguments
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 23:05:51 +0000 (20:05 -0300)]
screenShield: Cleanup unused method arguments

The 'velocity' argument is not used anymore, since the only
caller passing a different value than 0 was the drag motion
callback.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Remove the drag action from the shield
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 23:00:58 +0000 (20:00 -0300)]
screenShield: Remove the drag action from the shield

This is start of the end of the screen shield; start by
removing the dragging action from it.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Don't destroy on cancel
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 22:47:58 +0000 (19:47 -0300)]
unlockDialog: Don't destroy on cancel

Otherwise there will be no way to recover it in the future. Also
remove an else condition that assumed the dialog would destroy
itself on cancel.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Always show session's unlock dialog
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 22:30:02 +0000 (19:30 -0300)]
screenShield: Always show session's unlock dialog

Instead of destroying the dialog when the screen shield is
visible, and creating it when lifting the shield, always show
the session's unlock dialog.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Remove _lockScreenContents and family
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 22:25:55 +0000 (19:25 -0300)]
screenShield: Remove _lockScreenContents and family

It is not used anymore, and together with it, we don't need the
_ensureLockScreen() / _clearLockScreen() pair anymore too.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Blur background
Georges Basile Stavracas Neto [Tue, 7 Jan 2020 19:43:35 +0000 (16:43 -0300)]
unlockDialog: Blur background

Add a 200px blur with a 55% brightness to the unlock dialog
background.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Move background to Unlock Dialog
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 22:16:55 +0000 (19:16 -0300)]
screenShield: Move background to Unlock Dialog

In addition to that, remove the ClutterBoxLayout that is set as
the layout manager of the Unlock Dialog, and apply the primary
monitor constraint to the child St.BoxLayout instead.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Remove unused 'onPrimary' argument
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 21:53:46 +0000 (18:53 -0300)]
screenShield: Remove unused 'onPrimary' argument

The 'onPrimary' argument was being passed to dialog.open(). Turns out,
neither UnlockDialog nor LoginDialog use this parameter.

Remove the unnecessary 'onPrimary' parameter, and cleanup the related
code.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Move notifications to Unlock Dialog
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 21:35:13 +0000 (18:35 -0300)]
screenShield: Move notifications to Unlock Dialog

Also adjust the CSS style classes names to match the new owner.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog, loginDialog: Add a 'wake-up-screen' signal
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 21:22:55 +0000 (18:22 -0300)]
unlockDialog, loginDialog: Add a 'wake-up-screen' signal

The signal is currently present in the notifications box, but next
commits will move the notifications box to the unlock dialog.

Add a 'wake-up-screen' signal to the dialogs.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agounlockDialog: Adjust date format
Georges Basile Stavracas Neto [Mon, 10 Feb 2020 22:11:26 +0000 (19:11 -0300)]
unlockDialog: Adjust date format

As per design feedback at FOSDEM, adjust the time format to
not have a comma, nor padding.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Move clock to Unlock Dialog
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 21:16:53 +0000 (18:16 -0300)]
screenShield: Move clock to Unlock Dialog

Move the Screen Shield clock to Unlock Dialog. Also adjust
the CSS style classes names to match the new owner.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agoscreenShield: Remove arrows
Georges Basile Stavracas Neto [Thu, 28 Nov 2019 21:01:38 +0000 (18:01 -0300)]
screenShield: Remove arrows

They are not present anywhere in the new mockups.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/872

6 years agokeyboard: Only enable automatically if ClutterSeat::touch-mode is enabled
Carlos Garnacho [Mon, 10 Feb 2020 19:03:30 +0000 (20:03 +0100)]
keyboard: Only enable automatically if ClutterSeat::touch-mode is enabled

This defers the policy on backends about whether it makes sense to show
the OSK.

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/872
6 years agoUpdate Finnish translation
Jiri Grönroos [Mon, 10 Feb 2020 21:31:42 +0000 (21:31 +0000)]
Update Finnish translation

6 years agoUpdate Turkish translation
Emin Tufan Çetin [Mon, 10 Feb 2020 20:24:58 +0000 (20:24 +0000)]
Update Turkish translation

6 years agoUpdate Indonesian translation
Kukuh Syafaat [Mon, 10 Feb 2020 06:52:35 +0000 (06:52 +0000)]
Update Indonesian translation

6 years agoUpdate Galician translation
Fran Dieguez [Sun, 9 Feb 2020 22:26:45 +0000 (22:26 +0000)]
Update Galician translation

6 years agoUpdate Japanese translation
sicklylife [Sat, 8 Feb 2020 20:44:46 +0000 (20:44 +0000)]
Update Japanese translation

6 years agoUpdate Japanese translation
sicklylife [Sat, 8 Feb 2020 20:31:51 +0000 (20:31 +0000)]
Update Japanese translation

6 years agoUpdate British English translation
Bruce Cowan [Sat, 8 Feb 2020 13:03:04 +0000 (13:03 +0000)]
Update British English translation

6 years agoUpdated Lithuanian translation
Aurimas Černius [Sat, 8 Feb 2020 12:25:56 +0000 (14:25 +0200)]
Updated Lithuanian translation

6 years agoUpdate Basque translation
Asier Sarasua Garmendia [Sat, 8 Feb 2020 08:10:26 +0000 (08:10 +0000)]
Update Basque translation

6 years agoUpdate Persian translation
Danial Behzadi [Fri, 7 Feb 2020 22:06:14 +0000 (22:06 +0000)]
Update Persian translation

6 years agomagnifier: Make magnification factor changes animatable
Carlos Garnacho [Thu, 6 Feb 2020 13:21:14 +0000 (14:21 +0100)]
magnifier: Make magnification factor changes animatable

So we can seamlessly change between them through eg. keybindings.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/984

6 years agomagnifier: Implement pointer motion tracking differently
Carlos Garnacho [Thu, 6 Feb 2020 12:25:20 +0000 (13:25 +0100)]
magnifier: Implement pointer motion tracking differently

The use of the core idle monitor means that focus change events
are also delayed by keyboard interaction. Since the magnifier is
already in the business of pointer tracking, it's easy enough to
fire the pointer rest timeout from here, so focus changes are
accumulated and delayed.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/984

6 years agomagnifier: Animate focus/caret position changes
Carlos Garnacho [Thu, 6 Feb 2020 10:03:09 +0000 (11:03 +0100)]
magnifier: Animate focus/caret position changes

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/984

6 years agomagnifier: Add support for animating "scroll" on focus changes
Carlos Garnacho [Thu, 6 Feb 2020 10:00:44 +0000 (11:00 +0100)]
magnifier: Add support for animating "scroll" on focus changes

This is nice in that it provides a hint of the relative position of
the new focus area, as opposed to a sudden jump.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/984

6 years agomagnifier: Transform a11y events' coordinates by scale factor
Carlos Garnacho [Thu, 6 Feb 2020 09:59:20 +0000 (10:59 +0100)]
magnifier: Transform a11y events' coordinates by scale factor

We get those events in logical coordinates, which we have to transform
into actual pixels.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/984

6 years agomagnifier: Ignore repeated a11y events
Carlos Garnacho [Thu, 6 Feb 2020 09:56:44 +0000 (10:56 +0100)]
magnifier: Ignore repeated a11y events

We may get several a11y events setting the caret on the same
coordinates it previously was. Make focus tracking ignore those,
as we're jumping to the same coordinates again during eg. mouse
operation.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/984

6 years agomagnifier: Sanity check coordinates in scrollContentsTo
Carlos Garnacho [Thu, 6 Feb 2020 09:52:24 +0000 (10:52 +0100)]
magnifier: Sanity check coordinates in scrollContentsTo

We may receive a11y events with bogus coordinates (eg. x/y = minint),
so ensure the coordinates are sane before scrolling there.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/984

6 years agomagnifier: Clip all crosshair lines at even distances
Carlos Garnacho [Thu, 6 Feb 2020 09:38:50 +0000 (10:38 +0100)]
magnifier: Clip all crosshair lines at even distances

If the crosshair is clipped so it doesn't cover the pointer cursor,
the clip rectangle is skewed towards the bottom/right. This was
made so to accomodate the default pointer, but the unevenness stays
on other pointer cursors, and it makes the crosshair look odd on
short crosshair length.

Make all lines clip to an even distance from the center instead.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/984

6 years agomagnifier: Apply color inversion to crosshairs/pointer
Carlos Garnacho [Thu, 6 Feb 2020 09:33:27 +0000 (10:33 +0100)]
magnifier: Apply color inversion to crosshairs/pointer

It is somewhat unexpected that crosshair color and pointer cursor colors
remain the same across changes in color inversion settings, and may lead
to contrast issues. Apply the effect on the common container, so it
applies to these all.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/984

6 years agomagnifier: Apply scale factor to crosshair length
Carlos Garnacho [Thu, 6 Feb 2020 09:31:17 +0000 (10:31 +0100)]
magnifier: Apply scale factor to crosshair length

On hidpi displays the length is double as advertised, make it match
the advertised length.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/984

6 years agoUpdate Swedish translation
Anders Jonsson [Fri, 7 Feb 2020 15:02:26 +0000 (15:02 +0000)]
Update Swedish translation

6 years agoworkspace: Animate window clones using translation properties
Daniel van Vugt [Thu, 16 Jan 2020 10:42:50 +0000 (18:42 +0800)]
workspace: Animate window clones using translation properties

Instead of position x/y properties. This reduces CPU-intensive relayouts
in JavaScript (`vfunc_allocate` etc).

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1271
since the other fix required already landed in 4c4846e9.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/936

6 years agodnd: Make DND translation-property-aware
Daniel van Vugt [Wed, 22 Jan 2020 08:40:50 +0000 (16:40 +0800)]
dnd: Make DND translation-property-aware

Previously DND only worked properly for actors with zero translation.
But it only requires a small tweak to `this._dragOffsetX/Y` to support
non-zero translation values.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/936

6 years agoUpdate Persian translation
Danial Behzadi [Fri, 7 Feb 2020 13:04:10 +0000 (13:04 +0000)]
Update Persian translation

6 years agoiconGrid: Avoid animating the same icon twice
Daniel van Vugt [Fri, 7 Feb 2020 09:23:11 +0000 (17:23 +0800)]
iconGrid: Avoid animating the same icon twice

If the icon proper has opacity of zero then that's probably because a
clone of it is animating. So avoid animating the source actor too.

And if there's any other reason for the opacity being zero, still don't
animate it because we can't see it :)

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2167
6 years agoappDisplay: Call super.vfunc_unmap last
Daniel van Vugt [Fri, 7 Feb 2020 09:57:19 +0000 (17:57 +0800)]
appDisplay: Call super.vfunc_unmap last

So as to guarantee the unmapped state sticks and doesn't get toggled
back to mapped before we return.

Being in a mapped state when `FolderIcon.vfunc_unmap()` returned was
causing an assertion failure in `clutter_actor_set_mapped` and crashed
the shell.

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2170
6 years agoUpdated Spanish translation
Daniel Mustieles [Fri, 7 Feb 2020 10:54:07 +0000 (11:54 +0100)]
Updated Spanish translation

6 years agoMerge branch 'master' of gitlab.gnome.org:GNOME/gnome-shell
Daniel Mustieles [Fri, 7 Feb 2020 10:54:07 +0000 (11:54 +0100)]
Merge branch 'master' of gitlab.gnome.org:GNOME/gnome-shell

6 years agoUpdate Brazilian Portuguese translation
Rafael Fontenelle [Thu, 6 Feb 2020 23:47:17 +0000 (23:47 +0000)]
Update Brazilian Portuguese translation

6 years agoBump version to 3.35.90
Florian Müllner [Thu, 6 Feb 2020 20:02:17 +0000 (21:02 +0100)]
Bump version to 3.35.90

Update NEWS.

6 years agotheme: Get back .weather-header-box styling
nana-4 [Thu, 6 Feb 2020 13:18:01 +0000 (22:18 +0900)]
theme: Get back .weather-header-box styling

This introduced in f2df9f1a was lost in 9ea745bc.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/957

6 years agotheme: Move .world-clocks-button before .weather-button
nana-4 [Thu, 6 Feb 2020 13:15:19 +0000 (22:15 +0900)]
theme: Move .world-clocks-button before .weather-button

As per the layout.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/957

6 years agotheme/calendar: Don't nest all card styles for code consistency
nana-4 [Thu, 6 Feb 2020 13:08:33 +0000 (22:08 +0900)]
theme/calendar: Don't nest all card styles for code consistency

The inconsistent styling rules "some card styles are nested, but some
are not" and "some card styles are nested, but some of their descendant
styles are defined elsewhere" are very confusing.

This commit stops nesting all card styles to make the coding style
consistent and less confusing.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/957

6 years agotheme: Adjust calendar popover sizing
nana-4 [Thu, 6 Feb 2020 12:42:13 +0000 (21:42 +0900)]
theme: Adjust calendar popover sizing

- Remove bottom blank space on the right column of the calendar popover
  so that the weather card is bottom-aligned with the clear button on
  the left column.
- Remove top blank space on the left column of the calendar popover so
  that the message list is top-aligned with the today button on the
  right column.
- Adjust .message-list-controls sizing to align with other card-styled
  elements.
- Use regular `spacing` instead of margin for some spacing.

https://gitlab.gnome.org/GNOME/gnome-shell/issues/2088
Closes https://gitlab.gnome.org/GNOME/gnome-shell/issues/2120

6 years agotheme: Simplify .message styling
nana-4 [Tue, 4 Feb 2020 16:15:27 +0000 (01:15 +0900)]
theme: Simplify .message styling

- Use fewer properties for layout.
- Use .message-body instead of .message-content to change the body
  color, and remove some color overrides.
- Fix border-radius for last .message-media-control, not only on hover.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/957

6 years agotheme: Reorder selectors in .message
nana-4 [Tue, 4 Feb 2020 16:08:20 +0000 (01:08 +0900)]
theme: Reorder selectors in .message

The order was messed up when the recent Sass reorganization.
This reorders the selectors in .message to make sense again.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/957

6 years agotheme/notifications: Remove some duplicate or pointless styling
nana-4 [Tue, 4 Feb 2020 16:07:55 +0000 (01:07 +0900)]
theme/notifications: Remove some duplicate or pointless styling

Those styles are defined in .message and do not need to be overridden in
.notification-banner.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/957

6 years agotheme/notifications: Remove some unused style classes
nana-4 [Tue, 4 Feb 2020 16:07:04 +0000 (01:07 +0900)]
theme/notifications: Remove some unused style classes

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/957

6 years agotheme: Apply spacing to .overview-icon-with-label correctly
nana-4 [Tue, 4 Feb 2020 16:03:05 +0000 (01:03 +0900)]
theme: Apply spacing to .overview-icon-with-label correctly

- Remove margin-bottom for StIcon, which is not only ineffective, but
  also created a bug in app folders.
- Remove ">" which is invalid for overview icons that are not app
  folders.
- Apply spacing to the correct target "StBoxLayout", not the parent
  .overview-icon.overview-icon-with-label.

Fixes https://gitlab.gnome.org/GNOME/gnome-shell/issues/2129